Oklahoma NG911 Toolkit | Prep | [Enhancement] | Validation | MSAG | Comparison | Submission

Supplementary Documentation | Examples | Topology Rules | Change Log | Error Glossary

# Enhancement Toolset

## Toolset Credits

- Riley Baird, Oklahoma Transportation Cabinet
- Emma Baker, Oklahoma Transportation Cabinet

##### Last Revised:

January 09, 2025

## Abstract

These tools automate various tasks involved with data creation and/or modifications.

## Tools

### Calculate/Convert/Fix Field(s)

Calculate/Convert/Fix

- Tool calculates, converts, or fixes fields in Standard feature classes. More details provided below.

#### Usage

1. Select Standard geodatabase.
2. Select analysis.
3. Select required and/or optional parameters (see below for more information).
4. Execute the tool.

### Calculate/Convert/Fix Field(s) - Details

#### Common Across Tool

##### Street Fields

- Fields include `PreMod`, `PreDir`, `PreType`, `PreTypeSep`, `Street`, `StreetType`, `SufDir`, and `SufMod`.

##### Next-Gen Fields

- Fields include `Street`, `PreTyp`, `StreetType`, `PreDir` and `SufDir`.

##### Legacy Fields

- Fields include `LgcyStreet`, `LgcyPreTyp`, `LgcyType`, `LgcyPreDir` and `LgcySufDir`.

##### Side for Roads

- Options include `LEFT` ('L') and `RIGHT` ('R')

##### Variant Options

- 'NEXT-GEN' - Use and/or Calculate next-gen fields
- 'LEGACY' - Use and/or Calculate legacy fields

#### Calculate `FullName` and `LgcyFulSt`

- Calculates the `FullName` and `LgcyFulSt` fielda of the Address Point Standard feature class and/or the Road Centerline Standard feature class. For the `FullName` fields, the street fields are used with next-gen fields, and the legacy fields are replaced with the Legacy version of the fields for the `LgcyFulSt` field.

##### Usage (con't.)

- Select at least one of the Standard feature class names for analysis.
- Select at least one of the variant options for analysis.

#### Calculate `FullAddr` and `LgcyFulAdd`

- Calculates the `FullAddr` fand `LgcyFulAdd` fielda of the Address Point Standard feature class and/or the Road Centerline Standard feature class. For the `FullAddr` fields, the `AddNumPre`, `AddNumber`, `AddNumSuf`, plus the street fields are used, and the [legacy direction fields] and [legacy type fields] are preplaced with the Legacy version of the fields for the `LgcyFulAdd` field.

##### Usage (con't.)

- Select at least one of the variant options for analysis.

#### Calculate `Parity_L` and `Parity_R`

- Calculates the `Parity_`side fields of a road centerline feature class. The fields used for the calculation are: `Add_`side`_From` and `Add_`side`_To`. The tool will used the first and last digit on both sides to determine whether the number is `EVEN`, `ODD`, `BOTH`, or `ZERO`.

##### Usage (con't.)

- N/A

#### Calculate Null Values to N

- Calculates null values for fields with YESNO domain as `N`.

##### Usage (con't.)

- Select at least one of the Standard feature class names for analysis.

#### Calculate `RCLMatch` and `RCLSide`

- Requires the `RCLMatch` field. First, dataframes are created for the Address Point and Road Centerline featuer classes. Next, the street fields concatenated strings for each feature class. Then, the Road Centerline dataframe is joined to the Address Point dataframe using the street fields concatenated string. Non-matched address objects are then removed from the joined dataframe. Next, the `AddNumber` field value is then compare to the range of `Add_`side`_From` value to `Add_`side`_To` value with the `Partiy_`side used to determine the step number; this will determine the side of the road (`RCLSide`). Non-matches are then removed from the joined dataframe. The `PreNum` value is then compare the both `Add_`side`_Pre` value, and the `MSAGComm` field value is compared to the `MSAGComm_`side value. Once these comparisons are complete, the possible matches are returned. If only one match is returned, the `NGUID_RDCL` value is returned as `RCLMatch`. Values that results with ties start with the string `TIES` with the `NGUID_RDCL` values returned as a pipe-separated `local:agency` string. `RCLSide` is set to `NO MATCH` The rest of the non-matched values are populated as `NO MATCH`.

##### Usage (con't.)

- N/A

#### Calculate `MSAGComm`

- Calculate `MSAGComm` field for Address Point feature class and `MSAGComm_`side fields for Road Centerline feature class.

##### Usage (con't.)

- Select at least one of the Standard feature class names for analysis.

#### Convert Type (Legacy or Next-Gen)

- Convert Type next-gen fields/legacy fields based on the variant options. The Legacy option calculates the legacy fields from the next-gen fields, while the Next-Gen option calculates the next-gen fields from the legacy fields.

##### Usage (con't.)

- Select at least one of the Standard feature class names for analysis.
- Select one of the variant options for analysis.

#### Convert Direction (Legacy or Next-Gen)

- Convert Direction next-gen fields/legacy fields based on the variant options. The Legacy option calculates the legacy fields from the next-gen fields, while the Next-Gen option calculates the next-gen fields from the legacy fields.

##### Usage (con't.)

- Select at least one of the Standard feature class names for analysis.
- Select one of the variant options for analysis.

#### Fix Leading/Trailing Spaces

- Fix leading/trailing spaces in fields with TEXT type.

##### Usage (con't.)

- Select at least one of the Standard feature class names for analysis.

#### Fix Domain Case

- Fix values that match values in domain.

##### Usage (con't.)

- Select at least one of the Standard feature class names for analysis.

#### Fix Level Fields

- Fix FromLevel and/or ToLevel fields from number-version to text-version to match domain in Road Centerline feature class.

##### Usage (con't.)

- Select at least one of the Standard field names for analysis.

## Support Contact

For issues or questions, please contact through email Riley Baird at rbaird@odot.org or Emma Baker at ebaker@odot.org with the Oklahoma Transportation Cabinet, and please include in the email which script you were running, any error messages, and a zipped copy of your geodatabase. Change the file extension from `zip` to `piz` so it gets through the email server. If there are further data transfer issues, contact Emma or Riley to make alternative data transfer arrangements.

## Disclaimer

The Oklahoma NG9-1-1 GIS Toolbox is provided by the Oklahoma Geographic Information (GI) Council, Oklahoma 9-1-1 Management Authority, Oklahoma Department of Transportation (ODOT), Oklahoma Office of Geographic Information (OGI) , and associated contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the Oklahoma GI Council, Oklahoma 9-1-1 Management Authority, ODOT, OGI, or associated contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.